Parallel development of a software system

ABSTRACT

Software configuration management includes removing a selected section from a first artifact in a first stream. The first artifact includes a plurality of sections, and a second artifact in the first stream is created including the selected section. The second artifact does not include at least one other section of the plurality of sections. An annotation is generated using a processor that specifies the first artifact, a range within the first artifact corresponding to the selected section, and the second artifact into which the selected section is moved. The annotation is used to apply changes implemented in selected artifacts from one stream to another.

BACKGROUND

One or more embodiments disclosed within this specification relate toparallel development of a software system using a software configurationmanagement (SCM) system.

An SCM system helps to coordinate the actions of many developers whileworking on a complex software system. During the development process,the SCM system can manage operations such as version control among thevarious software assets that are generated and/or updated as part of thesoftware system under development. The SCM system further helps tocoordinate activities conducted across different versions of thesoftware system. For example, the SCM system can coordinate updates orfixes that must be carried forward from one release to the nextinclusive of updates or fixes that must be propagated from an olderrelease to a newer release still under development.

BRIEF SUMMARY

One or more embodiments disclosed within this specification relate toparallel development of a software system using a software configurationmanagement system.

An embodiment can include a method of software configuration management.The method can include removing a selected section from a first artifactin a first stream, wherein the first artifact includes a plurality ofsections, and creating a second artifact including the selected sectionin the first stream. At least one other section of the plurality ofsections is not included in the second artifact. An annotation can begenerated, using a processor, specifying the first artifact, a rangewithin the first artifact corresponding to the selected section, and thesecond artifact into which the selected section is moved.

Another embodiment can include a method of software configurationmanagement. The method can include selecting a first artifact in a firststream, including content of the first artifact within a second artifactin the first stream, and generating an annotation indicating that thefirst artifact no longer exists in the first stream and indicating thatthe second artifact includes the content of the first artifact using aprocessor.

Another embodiment can include a method of software configurationmanagement. The method can include selecting an artifact within a firstdirectory tree component within a first stream, creating a copy of theartifact within a second directory tree component within the firststream, and generating an annotation indicating that the copy of theartifact from the first directory tree component is included in thesecond directory tree component using a processor.

One or more other embodiments can include computer program products forsoftware configuration management. The computer program product(s) caninclude a computer readable storage medium having computer readableprogram code embodied therewith. The computer readable program code canbe configured to implement or perform the various functions and/oroperations disclosed within this specification.

One or more other embodiments can include a system configured forsoftware configuration management. The system can include a processorthat is configured to initiate the functions and/or operations describedwithin this specification.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a software configurationmanagement (SCM) system in accordance with an embodiment disclosedwithin this specification.

FIG. 2 is a block diagram illustrating an example of a split-out type ofSCM operation in accordance with another embodiment disclosed withinthis specification.

FIG. 3 is a flow chart illustrating a method of performing a split-outtype of SCM operation in accordance with another embodiment disclosedwithin this specification.

FIG. 4 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.

FIG. 5 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.

FIG. 6 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.

FIG. 7 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.

FIG. 8 is a block diagram illustrating an example of a combine type ofSCM operation in accordance with another embodiment disclosed withinthis specification.

FIG. 9 is a flow chart illustrating a method of performing a combinetype of SCM operation in accordance with another embodiment disclosedwithin this specification.

FIG. 10 is a block diagram illustrating an example of an SCM operationin accordance with another embodiment disclosed within thisspecification.

FIG. 11 is a block diagram illustrating an example of an SCM operationin accordance with another embodiment disclosed within thisspecification.

FIG. 12 is a flow chart illustrating a method of performing a copy typeof SCM operation in accordance with another embodiment disclosed withinthis specification.

FIG. 13 is a flow chart illustrating a method of performing SCMoperations in accordance with another embodiment disclosed within thisspecification.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied, e.g., stored,thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard diskdrive (HDD), a solid state drive (SSD), a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CD-ROM), a digital versatile disc (DVD), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber, cable, RF, etc., or any suitable combination ofthe foregoing. Computer program code for carrying out operations foraspects of the present invention may be written in any combination ofone or more programming languages, including an object orientedprogramming language such as Java™, Smalltalk, C++ or the like andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer, or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer, other programmable data processing apparatus,or other devices create means for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

One or more embodiments disclosed within this specification relate toparallel development of a software system using a software configurationmanagement (SCM) system. In accordance with one or more embodimentsdisclosed herein, an SCM system can be configured to perform one or moreoperations that allow changes to software assets to be implementedacross various logical boundaries that exist within the SCM system. Inimplementing the changes, any history of the related software assets canbe carried forward with the change despite the crossing of anyboundaries between versions, streams, or other types of logicalboundaries that may exist within the SCM system.

For example, content can be split-out of a particular software asset andplaced into a new software asset while retaining a traceable pathbetween the software asset from which content is removed and the newlycreated software asset into which the content is placed. In anotherexample, a software asset can be moved into another software assetleaving a traceable path indicating that the software asset is subsumedwithin the other software asset. By maintaining the traceable paths,further changes to the software system under development can beimplemented across streams, revisions, and the like.

For ease of illustration, the term “element” refers to software objectsor software assets that have a unique or a distinct identity within anSCM system. Examples of elements within an SCM system can include afile, also referred to as an “artifact,” and a “directory treecomponent.” Each element can be part of a software system beingdeveloped or maintained and can be tracked within the SCM systemindividually. For example, each element within an SCM system can have aunique identifier associated with the element for such trackingpurposes. The term “section,” as used within this specification, refersto a portion of a tracked element such as an artifact within the SCMsystem. For example, a section can refer to a portion of content of anartifact, such as text including, but not limited to, human readablesource code, or the like. A section, for example, can be an amount ofcontent from an artifact that is less than the entirety of the contentof the artifact. As such, a section is not tracked in and of itselfwithin the SCM system. Rather, tracking of a section can be performed bythe SCM system through comparison and/or matching functions or analysisof elements.

FIG. 1 is a block diagram illustrating an SCM system 105 in accordancewith an embodiment disclosed within this specification. In general, SCMsystem 105 can be implemented in the form of a data processing systemloaded with and/or executing an SCM application 150. As such, SCM system105 can include at least one processor 105 coupled to memory elements110 through a system bus 115. SCM system 105 can store program codewithin memory elements 110.

Processor 105 can execute the program code accessed from memory elements110 via system bus 115. In one aspect, for example, SCM system 105 canbe implemented as a computer that is suitable for storing and/orexecuting program code, e.g., a server or the like. It should beappreciated, however, that SCM system 105 can be implemented in the formof any system including a processor and memory that is capable ofperforming the functions described within this specification.

Memory elements 110 can include one or more physical memory devices suchas, for example, local memory 120 and one or more bulk storage devices125. Local memory 120 refers to RAM or other non-persistent memorydevice(s) generally used during actual execution of the program code.Bulk storage device(s) 125 can be implemented as a hard drive or otherpersistent data storage device. SCM system 105 also can include one ormore cache memories (not shown) that provide temporary storage of atleast some program code in order to reduce the number of times programcode must be retrieved from bulk storage device 125 during execution.

Input/output (I/O) devices such as a keyboard 130, a display 135, and apointing device (not shown) optionally can be coupled to SCM system 105.The I/O devices can be coupled to SCM system 105 either directly orthrough intervening I/O controllers. A network adapter 145 also can becoupled to SCM system 105 to enable SCM system 105 to become coupled toother systems, computer systems, remote printers, and/or remote storagedevices through intervening private or public networks. Modems, cablemodems, and Ethernet cards are examples of different types of networkadapters 145 that can be used with SCM system 105.

As pictured in FIG. 1, memory elements 110 can store SCM application150. SCM application 150, being implemented in the form of executableprogram code, can be executed by SCM system 105 to perform the variousfunctions and/or operations described within this specification. Itshould be appreciated that SCM system 105 can be configured to outputresults described herein in any of a variety of different ways. Forexample, “outputting” and/or “output” can mean storing in memoryelements 110, writing to a file stored in memory elements 110, writingto display 135 or other peripheral output device, playing audiblenotifications, sending or transmitting to another system such as one ormore client systems, exporting, or the like. Like numbers will be usedto refer to the same items throughout this specification.

SCM application 150, as executed by SCM system 105, can provide andimplement functions relating to the organization and tracking ofmultiple versions of a software system. SCM system 105, for example,facilitates the parallel and/or concurrent development of one or moredifferent versions, streams, and/or builds of a software system.

For example, as pictured in FIG. 1, SCM system 105 can include and mangestream 155 and stream 160 of a particular software system. Each stream,for example, can represent a software product or software environmentthat is being developed or maintained by one or more developers. Forinstance, stream 155 can represent a maintenance build of a softwaresystem. Stream 160 can represent a development build of the softwaresystem. It should be appreciated that SCM system 105 can maintain morethan one stream and that the number of streams shown is for purposes ofillustration only. For example, further streams can be managed relatingto different versions of the software system.

SCM system 105 can organize each of streams 155 and 160 according to anestablished hierarchy. For example, each of streams 155 and 160 caninclude one or more artifacts. Stream 155 is shown to include artifactA. Stream 160 is shown to include artifact A and artifact B. Eachartifact can include one or more sections. As noted, a section can referto a portion of content such as text including, but not limited to,human readable program code, e.g., source code. Artifact A of FIG. 1includes a changed section 165. In general, SCM system 105 can providevarious operations that enable the propagation of changed sections froman originating or source stream, e.g., stream 155, to a target stream,e.g., stream 160, despite the target stream including one or morerefactored changes therein.

In the example shown, artifact A within stream 155 can include one ormore different sections. Within stream 160, however, one or moresections that were previously included in artifact A of stream 155 havebeen refactored into different artifacts. More particularly, changedsection 165 in stream 155 is no longer located in artifact A in stream160, but rather in artifact B. Thus, in accordance with one or moreembodiments disclosed within this specification, changes detected inchanged section 165 can be applied to the appropriate artifact, e.g.,artifact B in stream 160, and to the appropriate portion or sectionwithin artifact B.

The case illustrated in FIG. 1 is provided for purposes of illustrationonly and, as such, is not intended to limit the one or more embodimentsdisclosed within this specification. Further operations and examples ofoperations are described with reference to the remaining figures. Forexample, SCM system 105 can implement operations including, but notlimited to, split-out, combine, and copy types of SCM operations andalso perform various other operations that may be required as aconsequence of implementing the split-out, combine, and/or copy types ofSCM operations.

FIG. 2 is a block diagram illustrating an example of a split-out type ofSCM operation in accordance with another embodiment disclosed withinthis specification. The split-out operation can be performed by the SCMsystem described herein. In general, FIG. 2 illustrates an artifact205_1 named ClassA.xxx. For purposes of illustration, the examplesdescribed throughout this specification utilize object orientedprogramming language conventions illustrated in source, or humanreadable, code. Often, object oriented programming language conventionsplace artifact structure requirements on the program code beingdeveloped. One common example is that the outer class of a portion ofprogram code typically is to be contained in an artifact having a namethat corresponds to, or is the same as, the class. Thus, ClassA, beingthe outer class, is included in artifact 205_1, which is namedClassA.xxx.

While developing a software system, it may be required that ClassB,which is included within ClassA, be refactored, or split-out, out ofClassA.xxx and placed into a newly generated artifact, e.g., artifact210_1 called ClassB.xxx. FIG. 2 illustrates that an SCM system cansplit-out ClassB from artifact 205_1 and create a new artifact calledClassB.xxx, e.g., artifact 210_1, in which ClassB is placed. Afterrefactoring, a new version of artifact 205 results indicated as artifact205_2, which can continue to be named ClassA.xxx. As shown, artifact205_2 no longer includes ClassB.

Within this specification, versions of artifacts generally are indicatedby the value following an underscore symbol (_). Thus, artifact 205 canhave a first version indicated by 205_1 and a second version indicatedby 205_2. In the context of a split-out operation, the split-outoperation is performed within a same stream. Thus, prior to thesplit-out operation, artifact 205_1 exists. After the split-outoperation, a new version of artifact 205 is created, which is denoted asartifact 205_2, and a new artifact is created, denoted as artifact210_1, e.g., a first version of the new artifact. The operations areperformed within a same stream.

In general, the section, e.g., content, that is removed from an artifactin performing a split-out operation can be referred to as the “split-outcontent.” In this example, the split-out content is ClassB in thatClassB is removed from artifact 205. Artifact 205_1 can be referred toas the “pre-split element.” The pre-split element refers to the artifactand version from which the split-out content is removed. Artifact 210can be referred to as the “post-split element.” The post-split elementrefers to the artifact and version that is created and into whichsplit-out content is placed while performing the split-out operation.

From time to time within this specification, reference made to aparticular artifact, e.g., artifact 205 or artifact 210, without theunderscore and following value corresponding to the version. In suchcases, reference to the artifact alone refers to the artifact in generalwithout reference to a particular version or without reference aparticular stream. The SCM system, for example, can track an “artifact”as an entity along with the various associated versions that may exist.In this regard, for example, an artifact can exist within one or moredifferent streams, with the artifact having one or more differentversions in each stream. Using the underscore following the referencenumber references a particular version of the artifact.

The split-out operation, as performed by the SCM system, furthergenerates metadata associated with, and describing, the split-outoperation that is performed. In one aspect, the metadata can be referredto as an annotation. With regard to a split-out type of SCM operation,the metadata that is generated by the SCM system can be referred to as a“split-link annotation” shown as split-link annotation 215. Split-linkannotation 215 can include an identifier signifying that the annotationis of the split-link type. Split-link annotation 215 can include, orspecify, the pre-split element (e.g., artifact 205_1) by specifying theartifact, version, and stream of the artifact from which the split-outcontent is taken.

Split-link annotation 215 further can include, or specify, the range ofcontent from the pre-split element that was refactored out and includedin the post-split element. More particularly, split-link annotation 215can include or specify the range, e.g., the bounds, of the split-outcontent in relation to artifact 205_1. For example, the range can bespecified in terms of a starting byte address and line number and anending byte address and line number of the split-out content as thatsplit-out content (e.g., ClassB) resided in the pre-split element(artifact 205_1). Referring to FIG. 2, the range can specify the byteaddress of the first character on the line starting ClassB and the linenumber to the byte address of the first character after the linecontaining the closing brace for ClassB and the line number.

Split-link annotation 215 also can include, or specify, the post-splitelement that is created by the split-out operation in terms of theartifact and version, e.g., artifact 210_1. As such, split-linkannotation 215 signifies that artifact 210_1 was generated as a resultof the SCM system performing a split-link operation using artifact 205_1as the pre-split element. For example, split-link annotation 215 canspecify the name and version of artifact 210_1. The split-out operationis performed within a same stream. As such, artifact 210_1 exists withinthe same stream as artifact 205_1 and 205_2. It should be appreciatedthat since split-link annotation 215 specifies artifact 205_1 as thepre-split element, the SCM system can infer or determine that artifact205_2 is the resulting version of the pre-split element generated inconsequence of removing the split-out content. Split-link annotation 215also can specify event information relating to the split-out operationsuch as the date and/or time that the split-out operation was performedand the particular user that initiated or requested the split-outoperation.

FIG. 3 is a flow chart illustrating a method 300 of performing asplit-out type of SCM operation in accordance with another embodimentdisclosed within this specification. Method 300 can be implemented bythe SCM system described herein. In step 305, a request for a split-outoperation can be received by the SCM system. The request can specify thepre-split element and the particular content to be split-out from thepre-split element.

In step 310, the SCM system can select the split-out content from withinthe pre-split element. In step 315, the SCM system can remove thesplit-out content, e.g., the selected content, from the pre-splitelement. In step 320, the SCM system can create the post-split element,e.g., a new artifact, within the current stream. As discussed, the newlycreated post-split element can be named according to any namingconventions required by the particular programming language that isbeing used. In step 325, the SCM system can include the split-outcontent within the newly created post-split element. In step 330, theSCM system can generate the split-link annotation. The split-linkannotation can be stored within the SCM system and, by virtue of theartifacts and/or versions referenced therein, can be determined to beassociated with one or more artifacts and/or particular versionsthereof.

Performance of one or more split-out operations can result in one ormore streams having components with split-link annotations. When the SCMsystem is directed to perform a merge of one stream with another, e.g.,a source stream with a target stream, the SCM system can identify thoseelements within the target stream that are associated with split-linkannotations and perform merge operations as described within thisspecification.

FIGS. 4-7 illustrate further examples of operations that can beperformed by an SCM system as disclosed within this specification systemrelating to split-out operations. FIG. 4 is a block diagram illustratingan example of an SCM operation in accordance with another embodimentdisclosed within this specification. For purposes of illustration,consider the case in which a split-out operation has been performed onartifact 205_1 in stream 1 resulting in the creation of artifact 205_2as described with reference to FIG. 2. For ease of illustration,indication of the stream of a particular artifact or version thereofwill be indicated, from time to time within this specification, byappending “-streamN” to the particular reference number, where “N”refers to the number of the stream in which the artifact or versionthereof is located.

Within a different stream, e.g., stream 2, artifact 205 exists in apre-split out state. More particularly, ClassB is still located withinartifact 205_1-stream2. Artifact 205_1-stream2 is modified therebyresulting in the creation of a second version denoted as artifact205_2-stream2. The change implemented within artifact 205_2-stream2 isillustrated in highlighting and is to be applied to stream 1 inconsequence of a merge request received by the SCM system. As noted,ClassB, however, has been split-out from artifact 205 in stream 2 from apreviously implemented split-out operation.

In carrying forward the change implemented in artifact 205_2-stream2 tostream 1, the SCM system can determine the change between artifact205_1-stream2 and artifact 205_2-stream2. The SCM system can determinethe change implemented and the location of the change implemented inartifact 205_2-stream2 as it relates to artifact 205_1-stream2.

The SCM system further can search for any split-link annotationsassociated with artifact 205. Annotations, in general, can be said torelate to particular artifacts. For example, an annotation can refer toone or more artifacts and specific versions of artifacts. In thisregard, the SCM system can search for an annotation relating to aparticular artifact regardless of version and/or stream. In other cases,the SCM system can search for an annotation relating to a specificartifact version and/or stream. In illustration, an annotation can belocated for, or from, any version of an artifact in any stream.

In this example, the SCM system can locate split-link annotation 215,which is associated with artifact 205. As discussed, split-linkannotation 215 indicates the pre-split element, e.g., artifact205_1-stream1. The SCM system then can determine whether the location ofthe change as implemented in artifact 205_2-stream2 is within the rangespecified in split-link annotation 215. It should be appreciated thatthe location of the change in artifact 205_2-stream2 can be correlatedwith a like or same location within the pre-split element, e.g.,artifact 205_1-stream1 (not shown).

In this example, the location of the change falls outside of the rangespecified in split-link annotation 215. As shown, the change in artifact205_2-stream2 is within ClassA and, as such, is to be implemented withinthe most recent version of artifact 205 in stream 1 after performance ofthe split-out operation, i.e., artifact 205_2-stream1, as opposed toartifact 210. Accordingly, the SCM can perform a merge operation inwhich the change to artifact 205_2-stream2 is implemented within, orapplied to, artifact 205_2-stream1 resulting in a new version ofartifact 205 shown as artifact 205_3 in stream 1.

FIG. 5 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.FIG. 5 illustrates an example in which the change implemented withinartifact 205_2-stream2 falls within the bounds of the range specified insplit-link annotation 215, e.g., within ClassB. As was the case in FIG.4, the change implemented within artifact 205_2-stream2 is to beimplemented within stream 1.

The SCM system can implement operations similar to those described withreference to FIG. 4. The SCM system can determine that the changeimplemented in artifact 205_2-stream2 is within the range specified insplit-link annotation 215, e.g., within the split-out content fromartifact 205_1-stream1. For example, the SCM system can compare theposition or location of the change implemented within artifact205_2-stream2 with the range specified in split-link annotation 215. Asshown, the change in artifact 205_2-stream2 is within ClassB and, assuch, the SCM system implements the change within artifact 210_1, asdetermined from split-link annotation 215. The SCM system can perform amerge operation in which the change to artifact 205_2-stream2 isimplemented within artifact 210_1-stream1 resulting in a new version ofartifact 210 shown as artifact 210_2 in stream 1.

FIG. 6 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.FIG. 6 illustrates an example in which the changes implemented withinartifact 205_2-stream2 fall within the bounds of the range specified insplit-link annotation 215, e.g., within ClassB, and also outside of thebounds, e.g., within ClassA. Again, the changes implemented withinartifact 205_2-stream2 are to be implemented within stream 1.

The SCM system can determine the changes between artifact 205_1-stream2and artifact 205_2-stream2. The SCM system can search for, and locate,split-link annotation 215 that specifies the correct pre-split element,e.g., artifact 205_1-stream1. The SCM system further can determinewhether the changes implemented in artifact 205_2-stream2 are within therange, e.g., at a location or position within the bounds specified, insplit-link annotation 215.

In this example, one of the changes made to artifact 205_2-stream2 hasbeen made to ClassA, e.g., outside of the range specified in split-linkannotation 215, and a second change to ClassB, e.g., inside the rangespecified in split-link annotation 215. As shown, the changes inartifact 205_2-stream2 are within both ClassA and ClassB. As such, theSCM system implements the change to ClassA within artifact 205_2-stream1resulting in artifact 205_3-stream1. The SCM system implements thechange to ClassB within artifact 210_1-stream1 resulting in artifact210_2-stream1.

FIG. 7 is a block diagram illustrating an example of an SCM operation inaccordance with another embodiment disclosed within this specification.FIG. 7 illustrates an example in which the change implemented withinartifact 205_2-stream2 occurs before, e.g., outside, the range specifiedby split-link annotation 215. The changes implemented within artifact205_2-stream2 are to be implemented within stream 1.

In one aspect, the SCM system can adjust the scope of the change or relyon a semantic analysis to determine that there is a change that needs tobe incorporated into artifact 205_2-stream1 and a change that needs tobe incorporated into artifact 210_1-stream1. Examples of changes inaccordance with those illustrated in FIG. 7 can include the introductionof one or more new pre-processor directives or one or more globalvariables that do not belong to any class but are valid changes to theartifact as a whole. In such cases, some of the changes may need to beapplied entirely to both artifact 205_2-stream1 and to artifact210_1-stream1, while other changes may need to be applied to artifact205_2-stream1 or to artifact 210_1-stream1.

The SCM system can determine the change(s) between artifact205_1-stream2 and artifact 205_2-stream2. The SCM system can search for,and locate, split-link annotation 215 that specifies the correctpre-split element, e.g., artifact 205_1-stream1. The SCM system furthercan determine whether the change implemented in artifact 205_2-stream2is within the scope of the change, e.g., within the range specified, insplit-link annotation 215.

In this example, one of the changes made to artifact 205_2-stream2 isdetermined, for example, through semantic analysis, to relate to ClassA.The line of code “import packageZ1,” for example, can be determined torelate to ClassA since ClassA includes a line of code that references“packageZ1.” The change relating to ClassA, therefore, can be consideredoutside of the range specified in split-link annotation 215. Another oneof the changes is determined, e.g., through semantic analysis, to relateto ClassB. The line of code “import packageZ2,” for example, can bedetermined to relate to ClassB since ClassB includes a line of code thatreferences “packageZ2.” The change relating to ClassB, therefore, can beconsidered to be within the range specified in split-link annotation215. Accordingly, the changes are determined to relate to both ClassAand to ClassB. As such, the SCM system can implement the change relatingto ClassA within artifact 205_2-stream1 resulting in artifact205_3-stream1. The SCM system can implement the change relating toClassB within artifact 210_1-stream1 resulting in artifact210_2-stream1.

FIG. 8 is a block diagram illustrating an example of a combine type ofSCM operation in accordance with another embodiment disclosed withinthis specification. The combine operation can be performed by the SCMsystem described herein. In general, FIG. 8 can follow the sameconventions described with reference to FIG. 2. For example, artifact805 can be named “ClassA.xxx”. Artifact 810 can be named ClassB.xxx. Ingeneral, a combine type of SCM operation can move one artifact intoanother artifact. In this example, the SCM system can move ClassB intoClassA as an inner class. The SCM system can move each section, e.g.,all content, of artifact 810_1 into artifact 805_1, thereby creatingartifact 805_2. Artifact 805_2 can retain the name ClassA.xxx. In thisexample, artifact 810_1 can be said to be the “contributing element” andartifact 805_2 can be said to be the “receiving element”.

In performing the combine operation, the SCM system can generate acombine-link annotation 815 that is associated with both artifact 810and artifact 805. Combine-link annotation 815 can include an identifierindicating that the annotation is of the “combine” type. Combine-linkannotation 815 can indicate, in general, that artifact 810_1, or thecontent thereof, has been incorporated into another artifact, in thiscase artifact 805_2. For example, combine-link annotation 815 canspecify information such as the contributing element, inclusive of theversion and/or stream of the contributing element, and a list of one ormore contributed ranges. Each range can describe the scope or content ofthe contribution, e.g., section, from the contributing element that isprovided to the receiving element. For example, each range can bespecified in the form of a starting byte address and line number of thecontributed content and an ending byte address and line number of thecontributed content, e.g., of ClassB in this case, with regard to thecontributing element. Thus, the ranges specify ranges within artifact810_1 that are contributed to artifact 805_2 within the same stream.

Combine-link annotation 815 also can specify the receiving element,e.g., the name and version updated by the operation. Combine-linkannotation 815 further can specify information such as the date and/ortime that the combine operation is performed and the user that requestedimplementation of the combine operation. As illustrated in FIG. 8, theability to include more than one range within combine-link annotation815 allows for sections of the contributing element to be ignored in themerge operation.

FIG. 9 is a flow chart illustrating a method 900 of performing a combinetype of SCM operation in accordance with another embodiment disclosedwithin this specification. Method 900 can be performed by the SCM asdescribed herein. In step 905, the SCM system can receive a request fora combine operation. The request can specify the contributing element,e.g., the component, and the receiving element, e.g., component. In step910, the SCM system can locate or identity the contributing element andthe receiving element. In step 915, the SCM system can select thecontent that is to be contributed to the receiving element from thecontributing element. In step 920, the SCM system can include thecontent from the contributing element in the receiving element. In step925, the SCM system can generate the combine-link annotation.

FIGS. 10-11 illustrate further examples of operations that can beperformed by the SCM system relating to combine operations. FIG. 10 is ablock diagram illustrating an example of an SCM operation in accordancewith another embodiment disclosed within this specification. Forpurposes of illustration, consider the case in which a combine operationas described with reference to FIG. 8 is performed in stream 1 onartifact 805_1, resulting in artifact 805_2. Within stream 2, artifact805_1 is modified thereby resulting in artifact 805_2-stream2, whichincludes the change. A user can request a merge operation in which thechange to artifact 805_2-stream2 is to be implemented or applied tostream 1.

Within artifact 805_2-stream2, a first change is specific to ClassA anda second change is not class-specific. The SCM system can determine thedifferences between artifact 805_1-stream2 and artifact 805_2-stream2.Accordingly, the SCM system can search for, and locate, combine-linkannotation 815. In general, using the combine-link annotation 815, theSCM system can determine whether the target stream, e.g., stream 1 inthis case, includes the receiving element.

When the changes implemented in artifact 805_2-stream2 are in any of thecontributed ranges specified in combine-link annotation 815, the SCMsystem can merge the changes into a new, e.g., a checked-out, version ofthe receiving element. In another example, when the differences are notin the range defined by the combine-link annotation, the SCM system canperform a semantic analysis of the differences and determine whether thechange should be merged into the receiving element.

In this example, the SCM system can perform a merge in which the changesto artifact 805_2-stream 2 are applied to artifact 805_2-stream 1.Accordingly, the SCM system can implement both changes to artifact805_2-stream1 resulting in artifact 805_3-stream1. For example, the SCMsystem can apply the changes to the most up-to-date version of artifact805 in stream 1, e.g., artifact 805_2-stream1, resulting in artifact805_3-stream1.

FIG. 11 is a block diagram illustrating an example of an SCM operationin accordance with another embodiment disclosed within thisspecification. For purposes of illustration, consider the case in whicha combine operation has been performed involving artifact 805 andartifact 810 in stream 1 as described with reference to FIG. 8. Withinstream 2, artifact 810 continues to exist and, further, has beenmodified as shown resulting in artifact 810_2-stream2. The changesimplemented in artifact 810_2-stream2 are to be carried forward tostream 1.

Within artifact 810_2-stream2, a first change is specific to ClassB anda second change is not class specific. The SCM system can determine thechange between artifact 810_1-stream2 and artifact 810_2-stream2. TheSCM system further can search for, and locate, combine-link annotation815. The SCM system determines that stream 1 no longer includes artifact810, per combine-link annotation 815. The SCM system can determine thatany changes to artifact 810_2-stream2 are to be implemented withinartifact 805_2-stream1 according to combine-link annotation 815.Accordingly, the changes to artifact 810_2-stream2 are applied toartifact 805_2-stream1 resulting in artifact 805_3-stream1. Asillustrated, the changes can be implemented within artifact 805_3-stream1 and are implemented at the appropriate locations, e.g., within ClassBand outside of ClassB.

FIG. 12 is a flow chart illustrating a method 1200 of performing a copytype of SCM operation in accordance with another embodiment disclosedwithin this specification. Method 1200 can be performed by the SCMsystem as described herein. In step 1205, a request for a copy operationcan be received by the SCM system. The request can specify theparticular artifact that is to be copied. For example, the request canspecify a particular artifact within a first directory tree componentand a second and different directory tree component as a target.

A “directory tree component” can refer to a snapshot of a hierarchicaldirectory for a particular software system being developed. As such, thedirectory tree component can specify directory structures, e.g.,hierarchies, and the particular artifact or artifacts included withineach directory tree component, inclusive of the location of the artifactor artifacts within the hierarchy specified.

In step 1210, the SCM system can locate or select the artifact that isto be copied. In step 1215, the SCM can create a copy of the selectedartifact within the second directory tree component. The seconddirectory tree component can be in the same stream as the firstdirectory tree component. In step 1220, the SCM system can generate acopy-link annotation associated with the artifact that is copied.

The copy-link annotation can indicate the directory tree component fromwhich the artifact is being copied, the directory tree component towhich the artifact is being copied, the artifact, inclusive of theversion, being copied, and the particular artifact (inclusive ofversion) that is created with the second directory tree component. Forexample, the path within the second directory tree component of thenewly created element, e.g., the copied element, can be specified.

FIG. 13 is a flow chart illustrating a method 1300 of performing SCMoperations in accordance with another embodiment disclosed within thisspecification. Method 1300 can be implemented by the SCM systemdescribed within this specification with reference to FIGS. 1-12. Method1300 provides an example of a technique for implementing merge typefunctions that operate across logical boundaries such as streams. Method1300 further accommodates a chain, e.g., a plurality, of split-outand/or combine types of SCM operations that may have been performed inone or more streams.

Method 1300 can begin in a state in which a request to merge streamswithin the SCM system has been received. The request, for example, canspecify that a merger of a second stream, e.g., a source stream, with afirst stream, e.g., a target stream, is to be performed. The methodillustrated in FIG. 13 can be performed across, or for each artifactthat is located within the source stream.

Method 1300 can start and, in step 1305, the SCM system can determinewhether there are any artifacts in the source stream that have not yetbeen processed. When one or more artifacts remain to be processed,method 1300 can proceed to step 1310. When no further artifacts in thesource stream remain to be processed, method 1300 can end. In step 1310,an artifact within the source stream that has not yet been processed canbe selected.

In step 1315, the SCM system can determine whether the selected artifacthas, or is associated with, an annotation. As noted, although anannotation can specify particular artifact versions included or involvedin a given SCM operation, the annotation itself can be associated withan artifact or artifacts in general. As such, the SCM can search for anannotation relating to a particular artifact such as the selectedartifact. When the SCM system determines that the selected artifact isassociated with an annotation, method 1300 can proceed to step 1325. Theannotation can be a split-link annotation or a combine-link type ofannotation. When the SCM system determines that the selected artifact isnot associated with an annotation, method 1300 can proceed to step 1320.

In step 1320, the SCM system can perform a merge operation on theselected artifact in which the selected artifact in the source stream ismerged with a corresponding artifact, e.g., a same named artifact,within the target stream. After step 1320, method 1300 can loop back tostep 1305 to continue processing another artifact in the source stream.

In step 1325, the SCM system can determine one or more changes betweenthe version of the selected artifact in the source stream that includesthe changes to be propagated to the target stream and a prior version ofthe artifact in the source stream. In step 1328, the SCM system candetermine whether there are any changes that have not yet beenprocessed. When there are changes that have not yet been processed,method 1300 can continue to step 1330. When no further changes remain,method 1300 can loop back to step 1305 to continue processing. In step1330, the SCM system can select a change identified in step 1325. Itshould be appreciated that during subsequent iterations through step1330, a “next” change can be selected.

In step 1335, the SCM system can determine whether the selected changeis within the range specified within the annotation. As noted, acomparison of the location and/or position of the change can beperformed with respect to the range specified within the annotation. Thelocation of the change in the version of the artifact within the sourcestream can be compared with the range specified in the annotation. Whenthe selected change is not within the range specified within theannotation, method 1300 can loop back to step 1320 and continueprocessing as described. In the case of a split-link annotation, forexample, the SCM determines that the change is not within a newlygenerated artifact within the target stream, but rather within a likenamed artifact within the target stream as described herein. When theselected change is within the range specified within the annotation,method 1300 can continue to step 1340.

In step 1340, the SCM can determine whether the artifact specifiedwithin the annotation exists within the target stream. In the case of asplit-link annotation, the SCM system can determine whether thepost-split element exists in the target stream. In the case of acombine-link annotation, the SCM system can determine whether thereceiving element exists within the target stream. When the artifactspecified within the annotation exists within the target stream, method1300 can proceed to step 1345. Otherwise, the selected change is notapplied and method 1300 can loop back to step 1328 to continueprocessing further changes.

In step 1345, the SCM system can determine whether the artifact locatedwithin the target stream is associated with an annotation. When theartifact within the target stream is also associated with an annotation,e.g., a second and further annotation, method 1300 can proceed to step1355. Otherwise, method 1300 can continue to step 1350. In step 1350,the SCM system can perform a merge of the change from the source streamto the element identified in step 1340 within the target stream. Afterstep 1350, method 1300 can loop back to step 1328 to continue processingfurther changes.

Continuing with step 1355, the SCM system can determine whether theselected change is in the range specified in the second annotation. Whenthe change is not in the range specified by the second annotation,method 1300 can proceed to step 1360, where the change can be mergedwith the component identified in step 1340 in the target stream.Otherwise, method 1300 can proceed to step 1365, where the SCM systemcan continue to determine whether any component specified by the secondannotation (e.g., a further receiving element or a further post-splitelement) is associated with a further, e.g., a third, annotation.

It should be appreciated that the SCM system can continue in thismanner, iteratively, until the further annotations are exhausted and/orresolved as described with reference to steps 1350 and/or 1360, e.g.,until the last artifact determined within located annotations is notassociated with a further annotation. Once this iterative procedure iscomplete or otherwise resolves, method 1300 can loop back to step 1328to continue processing.

The one or more embodiments described within this specification areillustrated in the context of an SCM. In another aspect, the one or moreembodiments can be utilized in any of a variety of different textmanagement systems in which one version of a textual work is composed ofmultiple files, e.g., artifacts. For example, one or more embodimentscan be applied or utilized within a document management system fordevelopment and/or tracking of different versions of literary works.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

For purposes of explanation, specific nomenclature is set forth toprovide a thorough understanding of the various inventive conceptsdisclosed herein. However, the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting of the invention. As used herein, the singular forms “a”,“an” and “the” are intended to include the plural forms as well, unlessthe context clearly indicates otherwise. As used herein, the term “if”may be construed to mean “when” or “upon” or “in response todetermining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

It will also be understood that the term “and/or” as used herein refersto and encompasses any and all possible combinations of one or more ofthe associated listed items. It will be further understood that theterms “includes” and/or “including,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will also be understoodthat, although the terms first, second, etc. may be used herein todescribe various elements, these elements should not be limited by theseterms, as these terms are only used to distinguish one element fromanother.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiments were chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A method of software configuration management, the method comprising:removing a selected section from a first artifact in a first stream,wherein the first artifact comprises a plurality of sections; creating asecond artifact including the selected section and not including atleast one other section of the plurality of sections in the firststream; and using a processor, generating an annotation specifying thefirst artifact, a range within the first artifact corresponding to theselected section, and the second artifact into which the selectedsection is moved.
 2. The method of claim 1, further comprising: applyinga change made in the first artifact located in a second stream to thesecond artifact in the first stream.
 3. The method of claim 2, furthercomprising: determining a change between a first version of the firstartifact and a second version of the first artifact in the secondstream; detecting the annotation associated with the first artifact; anddetermining whether the change is within the range in the annotation. 4.The method of claim 3, wherein determining whether the change is withinthe range in the annotation comprises: comparing a location of thechange implemented in the second version of the first artifact in thesecond stream with the range specified in the annotation.
 5. The methodof claim 4, further comprising: responsive to determining that thechange is within the range: locating the second artifact specified bythe annotation within the first stream; and implementing the change at alocation within the second artifact in the first stream corresponding tothe location of the change implemented in the second version of thefirst artifact in the second stream.
 6. The method of claim 1, furthercomprising: determining a change between a first version of the firstartifact and a second version of the first artifact in a second stream;detecting the annotation associated with the first artifact; determiningwhether the change is within the range in the annotation; and responsiveto determining that the change is not within the range, implementing thechange within the first artifact in the first stream.
 7. The method ofclaim 1, wherein the annotation specifies a version of the firstartifact from which the selected section is removed.
 8. The method ofclaim 1, wherein the annotation specifies a starting location of therange within the first artifact from which the selected section isremoved and an ending location of the range within the first artifactfrom which the selected section is removed.
 9. The method of claim 1,wherein the annotation specifies the second artifact into which theselected section is moved and event information corresponding to asplit-out event initiating removal of the selected section.
 10. A methodof software configuration management, the method comprising: selecting afirst artifact in a first stream; including content of the firstartifact within a second artifact in the first stream; and using aprocessor, generating an annotation indicating that the first artifactno longer exists in the first stream and indicating that the secondartifact includes the content of the first artifact.
 11. The method ofclaim 10, further comprising: determining a change between a firstversion of the first artifact and a second version of the first artifactin a second stream; detecting the annotation associated with the firstartifact; determining that the first artifact does not exist in thefirst stream according to the annotation; selecting the second artifactin the first stream according to the annotation; and implementing thechange in the second artifact in the first stream.
 12. The method ofclaim 11, wherein implementing the change in the second artifact in thefirst stream further comprises: making the change to the content in thesecond artifact in the first stream that was included from the firstartifact.
 13. The method of claim 10, wherein the annotation specifies astarting location and an ending location defining a range within thefirst artifact of content that is included in the second artifact.
 14. Amethod of software configuration management, the method comprising:selecting an artifact within a first directory tree component within afirst stream; creating a copy of the artifact within a second directorytree component within the first stream; and using a processor,generating an annotation indicating that the copy of the artifact fromthe first directory tree component is included in the second directorytree component.
 15. The method of claim 14, further comprising:determining a change between a first version of the artifact and asecond version of the artifact in a second stream; and applying thechange to the copy of the artifact within the second directory treecomponent. 16-25. (canceled)